Fix/scrape empty fields - #23
Merged
Merged
Conversation
… dynamic and static scrapers
…ages, forms, and scripts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix scrape results returning empty data for content_type, headers, cookies, links, images, forms, and scripts. The core scrapers (static and dynamic) were not capturing HTTP response metadata or extracting HTML elements, and the service layer hardcoded all these fields to empty defaults ("", {}, []).
Changes:
Related Issue
Addresses scrape data incompleteness: content_type always empty, headers/cookies always {}, links/images/forms/scripts always [].
Type of Change
Checklist
Verification